IMO this should actually be the default behaviour but it’s an “interface” change. This or setting the timeout to max int and exposing it as configurable.

I think the build failed on jenkins due to this infinite loop warning from FindBugs: https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/8934/findbugsResult/ . And indeed it is an infinite loop by design.
The other option could be to make the timeout in ConsumerPerformance configurable at the cli... Atm it’s hard coded to stop consuming if their haven’t been any new messages in 1 second.

It was pointed out the old consumer code path was invalid due to the iterator pattern that I hadn''t noticed (as opposed to the new consumer poll pattern). It's an option to just remove it from the old consumer code path.

Please check out this PR #4818, gonna be merged soon. And KIP-281: https://cwiki.apache.org/confluence/display/KAFKA/KIP-281%3A+ConsumerPerformance%3A+Increase+Polling+Loop+Timeout+and+Make+It+Reachable+by+the+End+User , and also https://issues.apache.org/jira/browse/KAFKA-6743

Hello is this still an issue?

This PR is being marked as stale since it has not had any activity in 90 days. If you
would like to keep this PR alive, please leave a comment asking for a review. If the PR has
merge conflicts, update it with the latest from the base branch.

If you are having difficulty finding a reviewer, please reach out on the [mailing list](https://kafka.apache.org/contact).

If this PR is no longer valid or desired, please feel free to close it. If no activity occurs in the next 30 days, it will be automatically closed.

This PR has been closed since it has not had any activity in 120 days. If you feel like this
was a mistake, or you would like to continue working on it, please feel free to re-open the
PR and ask for a review.